UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

tc Server VCO must produce log records that contain sufficient information to establish the outcome (success or failure) of events.


Overview

Finding ID Version Rule ID IA Controls Severity
V-240765 VRAU-TC-000225 SV-240765r879567_rule Medium
Description
After a security incident has occurred, investigators will often review log files to determine what happened. tc Server HORIZON must create a log entry when users access the system, and the system authenticates the users. The logs must contain information about user sessions to include what type of event occurred, when (date and time) events occurred, where within the server the events occurred, the client source of the events, the outcome (success or failure) of the event, the identity of the user/subject/process associated with the event. Like all web servers, tc Server generates HTTP status codes. The status code is a 3-digit indicator of the outcome of the server's response to the request.
STIG Date
VMware vRealize Automation 7.x tc Server Security Technical Implementation Guide 2023-10-03

Details

Check Text ( C-43998r674417_chk )
At the command prompt, execute the following command:

tail /storage/log/vmware/vco/app-server/localhost_access_log.txt

If the HTTP status codes are not being recorded, this is a finding.

Note: HTTP status codes are 3-digit codes, which are recorded immediately after "HTTP/1.1"
Fix Text (F-43957r674038_fix)
Navigate to and open /etc/vco/app-server/server.xml.

Navigate to and locate .

Configure the node with the below.

Note: The "AccessLogValve" should be configured as follows:
directory="logs"
pattern="%h %l %u %t "%r" %s %b"
prefix="localhost_access_log."
suffix=".txt"/>